Task grouping by context

ABSTRACT

In an approach to grouping tasks initialized by a first user, one or more computer processors receive a first task initialization by a first user. The one or more computer processors determine whether one or more additional tasks contained in one or more task groups are in use by the first user. Responsive to determining one or more additional tasks contained in one or more task groups are in use, the one or more computer processors determine whether the first task is related to at least one task of the one or more additional tasks. Responsive to determining the first task is related to at least one task of the one or more additional tasks, the one or more computer processors add the first task to the task group containing the at least one related task of the one or more additional tasks.

FIELD OF THE INVENTION

The present invention relates generally to the field of computer taskmanagement, and more particularly to grouping related tasks.

BACKGROUND

Computing equipment, particularly Personal Computers (PC's), are beingprovided with increasing multitasking capabilities, whereby multipleapplications can be opened at the same time, and applications in thebackground can continue to run as processor time is available.Applications have taken advantage of this multitasking capability byintroducing multitasking models. Applications are utilizing the tabsmethod to create user friendly multitasking while having the user staywithin one application. Whether the application is a web browser, a wordprocessing application, or an email application, users can navigatethrough a number of instances within each application and a number ofdifferent applications, all of which may be open at the same time on asingle computer.

A task-focused interface is a type of user interface which extends thedesktop metaphor of the graphical user interface to make tasks, notfiles and folders, the primary unit of interaction. Instead of showingentire hierarchies of information, such as a tree of documents, atask-focused interface shows the subset of the tree that is relevant tothe task-at-hand. This addresses the problem of information overloadwhen dealing with large hierarchies, such as those in software systemsor large sets of documents.

SUMMARY

Embodiments of the present invention disclose a method for groupingtasks initialized by a first user. One or more computer processorsreceive a first task initialization by a first user. The one or morecomputer processors determine whether one or more additional taskscontained in one or more task groups are in use by the first user.Responsive to determining one or more additional tasks contained in oneor more task groups are in use, the one or more computer processorsdetermine whether the first task is related to at least one task of theone or more additional tasks. Responsive to determining the first taskis related to at least one task of the one or more additional tasks, theone or more computer processors add the first task to the task groupcontaining the at least one related task of the one or more additionaltasks.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating a distributed dataprocessing environment, in accordance with an embodiment of the presentinvention.

FIG. 2 is a flowchart depicting operational steps of a context switchmanager, on a client computing device within the distributed dataprocessing environment of FIG. 1, for grouping related tasks, inaccordance with an embodiment of the present invention.

FIG. 3 illustrates an example of the operation of the context switchmanager of FIG. 2 inserted on a client computing device within thedistributed data processing environment of FIG. 1, in accordance with anembodiment of the present invention.

FIG. 4 illustrates an example of a graphical user interface of thecontext switch manager of FIG. 2 displayed, via a user interface, on aclient computing device within the distributed data processingenvironment of FIG. 1, in accordance with an embodiment of the presentinvention.

FIG. 5 depicts a block diagram of components of the client computingdevice executing the context switch manager, in accordance with anembodiment of the present invention.

DETAILED DESCRIPTION

In a fast-changing and developing world, computer-based jobs often comewith a very diverse work portfolio. Therefore there is a high risk ofinterrupts and context switches throughout a work day. There existdifferent types of taskbars in various operating systems, but, ingeneral, taskbars only list the number and type of open applications andprocesses. There are other tools for “Getting Things Done” (GTD), whichhelp track items on a “to do” list, however the GTD tools generally donot aid the user by showing how tasks are related.

Embodiments of the present invention recognize that efficiency can begained by implementing a tool that groups tasks which belong to a commonwork assignment. Implementation of embodiments of the invention may takea variety of forms, and exemplary implementation details are discussedsubsequently with reference to the Figures.

The present invention will now be described in detail with reference tothe Figures. FIG. 1 is a functional block diagram illustrating adistributed data processing environment, generally designated 100, inaccordance with one embodiment of the present invention. FIG. 1 providesonly an illustration of one implementation and does not imply anylimitations with regard to the environments in which differentembodiments may be implemented. Many modifications to the depictedenvironment may be made by those skilled in the art without departingfrom the scope of the invention as recited by the claims.

Distributed data processing environment 100 includes server computer 104and client computing device 108, interconnected over network 102.Network 102 can be, for example, a local area network (LAN), a wide areanetwork (WAN), such as the Internet, or a combination of the two, andcan include wired, wireless, or fiber optic connections. In general,network 102 can be any combination of connections and protocols thatwill support communications between server computer 104 and clientcomputing device 108.

Server computer 104 may be a management server, a web server, or anyother electronic device or computing system capable of receiving andsending data. In other embodiments, server computer 104 may represent aserver computing system utilizing multiple computers as a server system,such as in a cloud computing environment. In another embodiment, servercomputer 104 may be a laptop computer, a tablet computer, a netbookcomputer, a personal computer (PC), a desktop computer, a personaldigital assistant (PDA), a smart phone, or any programmable electronicdevice capable of communicating with client computing device 108 vianetwork 102. In another embodiment, server computer 104 represents acomputing system utilizing clustered computers and components to act asa single pool of seamless resources. Server computer 104 includesdatabase 106.

Database 106 resides on server computer 104. In another embodiment,database 106 may reside on client computing device 108, or on anotherdevice or component within distributed data processing environment 100accessible via network 102. A database is an organized collection ofdata. Database 106 can be implemented with any type of storage devicecapable of storing data that may be accessed and utilized by servercomputer 104, such as a database server, a hard disk drive, or a flashmemory. In other embodiments, database 106 can represent multiplestorage devices within server computer 104. Information stored ondatabase 106 may include directories for data and documents used byclient computing device 108, via network 102. The directories and datastored on database 106 may be accessed by users of other clientcomputing devices in distributed data processing environment 100 (notshown).

Client computing device 108 may be a desktop computer, a laptopcomputer, a tablet computer, a specialized computer server, a smartphone, or any programmable electronic device capable of communicatingwith server computer 104 via network 102 and with various components anddevices within distributed data processing environment 100. In general,client computing device 108 represents any programmable electronicdevice or combination of programmable electronic devices capable ofexecuting machine-readable program instructions and communicating withother computing devices via a network, such as network 102. Clientcomputing device 108 includes user interface 110, application(s) 112,and context switch manager 114. Client computing device 108 may includeinternal and external hardware components, as depicted and described infurther detail with respect to FIG. 5.

User interface 110 is a program that provides an interface between auser of client computing device 108 and context switch manager 114. Userinterface 110 may also provide an interface between context switchmanager 114 and database 106 on server computer 104, via network 102. Auser interface, such as user interface 110, refers to the information(such as graphic, text, and sound) a program presents to a user and thecontrol sequences the user employs to control the program. There aremany known types of user interfaces. In one embodiment, user interface110 is a graphical user interface (GUI). A GUI is a type of userinterface that allows users to interact with electronic devices, such asa computer keyboard and mouse, through graphical icons and visualindicators, such as secondary notation, as opposed to text-basedinterfaces, typed command labels, or text navigation. In computing, GUIswere introduced in reaction to the perceived steep learning curve ofcommand-line interfaces which require commands to be typed on thekeyboard. The actions in GUIs are often performed through directmanipulation of the graphical elements.

Application(s) 112 are one or more of a plurality of programs that auser of client computing device 108 may access to perform tasks includedin work assignments. Examples of application(s) 112 include, but are notlimited to, an email application, a web browser, a word processingprogram, a spreadsheet program, a presentation program, etc. In oneembodiment, application(s) 112 reside on client computing device 108. Inanother embodiment, one or more of application(s) 112 may reside onserver computer 104, or other computing devices in data processingenvironment 100, provided the other computing devices can communicatewith client computing device 108 via network 102.

Context switch manager 114 is a tool for grouping related tasks whichbelong to a common work assignment into task groups based on context,instead of a user having to declare that tasks are related. Tasks arespecial, interactive processes or threads that represent work units thatbelong to a work assignment. In general, a task may be a window of anapplication, a tab within a window, or a process that has a userinterface. Context switch manager 114 supports scheduling decisions inenvironments where a user runs multiple tasks, and only one of theuser's tasks is in focus at a particular point in time. A task is infocus when the user initializes the task. Also, a particular task is infocus while the user is actively utilizing that particular task. Contextswitch manager 114 tracks open tasks and applications through events,interruptions, and context switches to keep related tasks, andassociated “to dos”, organized for a user. Context switch manager 114assigns tasks to groups based on a pre-defined set of rules. Contextswitch manager 114 may display the related tasks as groups in a tray fora user to easily review what tasks are open and switch from one workassignment to another. Context switch manager 114 is depicted anddescribed in further detail with respect to FIG. 2.

FIG. 2 is a flowchart depicting operational steps of context switchmanager 114, on client computing device 108 within data processingenvironment 100 of FIG. 1, for grouping related tasks, in accordancewith an embodiment of the present invention.

Context switch manager 114 receives a task initialization (step 202). Atask may be initialized by opening application(s) 112. A task may alsobe initialized by batch processing in the background or network activitythat leads to tasks being opened. As a user of client computing device108 initializes a task, context switch manager 114 detects the new task.As discussed earlier, a task may be a window of an application, such asapplication(s) 112. For example, the user may open a file in a wordprocessing program. The file is considered a task that is part of a workassignment. Another example of a task initialization is the launching ofa web browser to a particular website. The initialized task is now thetask in focus.

Context switch manager 114 determines whether other tasks are open(decision block 204). In order to determine whether to group tasks,context switch manager 114 first determines whether other open tasks andtask groups exist. If no other tasks are open (no branch, decision block204), then context switch manager 114 generates a new task group (step206).

If context switch manager 114 determines that one or more tasks are open(yes branch, decision block 204), then context switch manager 114determines whether the resource used by the newly initialized task isthe same or related to the resource of a task in an existing task group(decision block 208). Resources may include files, folders, directories,network ports, semaphores, sockets, pipes, etc. Resources may alsoinclude tags, for example as used in tag clouds. Tasks can be consideredrelated if two tasks share the same resources. For example, common filesare a shared resource, therefore the files are related. Resources whoseIDs match a certain pattern may be considered related resources. Forexample, two files of the same name but with different suffixes, i.e.abc.txt and abc.xls, may be considered related resources. In a furtherexample, two tasks can be considered to share resources if they access,or open, the same resource or related resources. Tasks can also becomputationally related. For example, tasks with a parent/childrelationship can be considered related. Tasks can also be consideredrelated if they concern the same subject matter.

If the resources used by the newly initialized task are not related toan open task (no branch, decision block 208), then context switchmanager 114 determines whether an event was detected (decision block210). In one embodiment, an event may be an interruption, such as anaction not initiated by the user. For example, a pop-up screen of aninstant messenger program or an advertisement on a website may be aninterruption. Another example of an interruption is a time out such as ascreen saver or automatic hibernate after a period of inactivity. Inanother embodiment, an event can be user-initiated. For example, beforethe user leaves the office, the user logs out from or hibernates clientcomputing device 108 so that client computing device 108 is locked whilethe user is absent. In another embodiment, the closing of a previouslyexisting task group just prior to the initialization of the task infocus may be an event. For example, when the user closes the last taskin a task group when the work assignment associated with that task groupis complete, just prior to initializing a new task, the closing of thetask group may be considered an event. In another embodiment, the usermay define certain activities as events. For example, the user maydefine the email program to be an event such that when the user receivesor opens an email, context switch manager 114 detects an event.

If context switch manager 114 does not detect an event (no branch,decision block 210), then context switch manager 114 adds the task infocus to the current task group (step 212). The current task group isthe task group in which the previous task in focus belongs. The new taskis added to the current task group because of the likelihood that thenew task is part of the same work assignment as the previous task infocus due to the succession in which the tasks are opened, i.e. theprevious task in focus was opened immediately prior to theinitialization of the current task in focus. If context switch manager114 detects an event (yes branch, decision block 210), then contextswitch manager 114 generates a new task group (step 206).

Responsive to generating a new task group, context switch manager addsthe task in focus to the new task group (step 214).

If, responsive to determining one or more tasks are open (yes branch,decision block 204), and context switch manager 114 determines that thetask in focus uses the same or related resources to one or more of theopen tasks (yes branch, decision block 208), then context switch manager114 determines whether the task in focus shares related resources withmore than one task group (decision block 216). If the task in focus doesshare resources with more than one task group (yes branch, decisionblock 216), then context switch manager 114 merges the task groups (step218). For example, if the task in focus shares one resource with taskgroup A and a different resource with task group B, then context switchmanager 114 merges task group A with task group B. If the user prefersto keep related task groups separate, the user may override the mergeperformed by context switch manager 114.

Responsive to merging related task groups or determining that the taskin focus does not share related resources with more than one task group(no branch, decision block 216), context switch manager 114 adds thetask in focus to the related task group (step 220). The related taskgroup may be the current task group, the merged task group, or apreviously generated task group.

Responsive to adding the task in focus to the current, a related, or anew task group, context switch manager 114 updates the task group list(step 222). Context switch manager 114 maintains a list of each task ineach task group. As a new task is initialized, context switch manager114 updates the appropriate task group list. A user may reassign a taskto a different task group if the user decides context switch manager 114has assigned a task to an inappropriate task group.

Context switch manager 114 determines if the current task group isrelated to one or more other task groups (decision block 224). If amember task of the current task group uses the same or related resourcesof at least one task in another task group, context switch manager 114determines if the two task groups are related. If context switch manager114 determines that the current task group is related to one or moreother task groups (yes branch, decision block 224), context switchmanager 114 merges the related task groups (step 226).

Responsive to merging related task groups or if context switch manager114 determines there are no related task groups (no branch, decisionblock 224), context switch manager 114 determines if a new task isinitialized (decision block 228). If context switch manager 114determines that a new task is not initialized (no branch, decision block228), then context switch manager 114 completes execution and ends. Ifcontext switch manager 114 determines that a new task is initialized(yes branch, decision block 228), then context switch manager 114returns to step 202.

FIG. 3 illustrates an example of the operation of context switch manager114 inserted on client computing device 108 within data processingenvironment 100 of FIG. 1, in accordance with an embodiment of thepresent invention.

In example 300, each rectangle represents a unique task. Similarpatterns inside the rectangle indicate tasks within the same task group.Task groups are also shown within numbered brackets. The jagged arrowsindicate an event or an interruption. The long, arched arrows indicatethe continuation of a task or task group. The long, straight arrowrepresents the passing of time. The progression of the tasks in example300 is presented with respect to the steps described earlier withrespect to FIG. 2.

A user begins task 1, making task 1 the task in focus. Task 1 may be aword processing document in a directory named “Travel”. Context switchmanager 114 generates a new task group, task group 310, per step 206,because there are no other open tasks, per decision block 204. The userthen begins task 2, making task 2 the task in focus. Task 2 is a seconddocument from the directory named “Travel”. Task 2 is added to taskgroup 310 with task 1, per step 220, because task 1 and task 2 share arelated resource, i.e. files in the same directory, per decision block208. After task 2 opens, an interruption occurs. The interruption may bethe receipt of an email or an instant message.

Following the interruption, the user begins task 3, making task 3 thetask in focus. Task 3 may be a tab in a web browser. Context switchmanager 114 generates a new task group, task group 320, per step 206,because task 3 does not share resources with the tasks in task group310, per decision block 208, and the initialization of task 3 occurredafter an event, per decision block 210.

The user begins task 4, making task 4 the task in focus. Task 4 may be asecond tab in the web browser. Context switch manager 114 adds task 4 totask group 320 with task 3, per step 212, because task 3 and task 4 donot share a related resource, per decision block 208, and task 4 did notbegin following an event, per decision block 210.

The user begins task 5, making task 5 the task in focus. Task 5 may be aspreadsheet in the directory named “Travel”. Context switch manager 114adds task 5 to task group 310, per step 220, because task 5 shares arelated resource with tasks 1 and 2, i.e. files in the same directory,per decision block 208. The user then begins task 6, making task 6 thetask in focus. Task 6 is a presentation document from the directorynamed “Travel”. Context switch manager adds Task 6 to task group 310with tasks 1, 2, and 5, per step 220, because tasks 1, 2, 5, and 6 sharea related resource, i.e. files in the same directory, per decision block208. After task 6 opens, an event occurs. The event may be the userlocking client computing device 108 to take a break.

Following the event, the user begins task 7, making task 7 the task infocus. Task 7 may be a Portable Document Format (PDF) file in adirectory named “Salary”. Context switch manager 114 generates a newtask group, task group 330, per step 206, because task 7 does not shareresources with the tasks in task group 310 or task group 320, perdecision block 208, and the initialization of task 7 occurred after anevent, per decision block 210.

The user begins task 8, followed by task 9. Both task 8 and task 9 arePDF files in the directory named “Salary”. Context switch manager 114adds tasks 8 and 9 to task group 330, per step 220, because tasks 7, 8,and 9 share a related resource, i.e. files in the same directory, perdecision block 208.

The user returns to task 1 in task group 310. The user clicks a link inthe task 1 word processing document that opens a new browser tab. Thenew browser tab is task 10, and task 10 is now the task in focus.Context switch manager 114 adds task 10 to task group 310, per step 212,because the new task is added to the current task group when the twotasks do not share a resource, per decision block 208, and no event wasdetected, per decision block 210.

FIG. 4 illustrates an example of context switch manager 114 displayed,via user interface 110, on client computing device 108 within dataprocessing environment 100 of FIG. 1, in accordance with an embodimentof the present invention.

In the embodiment depicted in example 400, context switch manager 114 isdisplayed, via user interface 110, as a “tray” on the right side of ascreen associated with client computing device 108. The trayautomatically collects all applications and processes, and currentstate. Within the tray, all tasks, i.e. open applications and processes,are displayed by windows or tabs within windows. Each task may bedisplayed as a minimized screen shot (thumbnail) or an icon, with a nameand a last modified time stamp, to allow for easy recognition by theuser. Tasks are grouped, with each group representing a work assignment.A user may move a task from one task group to another by dragging anddropping the task with a mouse. One or more applications or tasks may bepre-configured to belong to the same task group. Within a task group,task thumbnails may be stacked according to the time they were openedand/or last modified and saved with the full state. Task groups 1, 2, 3,and 4 are shown in the tray. An enlarged view of task group 3 is shownin the center of the desktop. This represents the view a user sees whenthe user hovers a mouse over the task group in the tray.

A user may close a task group by clicking on the “close” icon, shown asan “X” in a circle in example 400. When the user clicks the close icon,context switch manager 114 closes the tasks in the task group, savingthe current state for each task. A user may manually create a task groupby clicking on the “create task group” button, shown below the tray.Context switch manager 114 prompts the user to either open the preferredtasks or to specify which tasks to open.

Context switch manager 114 may alert the user if context switch manager114 detects a period of inactivity that exceeds a pre-defined thresholdfor a particular task or task group. The user may define as well aschange the threshold per the user's preference. Context switch manager114 may alert the user visually. For example, context switch manager 114may cause the task group icon in the tray to flash. Context switchmanager 114 may also alert the user audibly. For example, context switchmanager 114 may cause client computing device 108 to emit a sound to getthe attention of the user. The user may customize the type, time, andlength of the alert.

FIG. 5 depicts a block diagram of components of client computing device108 in accordance with an illustrative embodiment of the presentinvention. It should be appreciated that FIG. 5 provides only anillustration of one implementation and does not imply any limitationswith regard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be made.

Client computing device 108 includes communications fabric 502, whichprovides communications between computer processor(s) 504, memory 506,persistent storage 508, communications unit 510, and input/output (I/O)interface(s) 512. Communications fabric 502 can be implemented with anyarchitecture designed for passing data and/or control informationbetween processors (such as microprocessors, communications, and networkprocessors, etc.), system memory, peripheral devices, and any otherhardware components within a system. For example, communications fabric502 can be implemented with one or more buses.

Memory 506 and persistent storage 508 are computer readable storagemedia. In this embodiment, memory 506 includes random access memory(RAM) 514 and cache memory 516. In general, memory 506 can include anysuitable volatile or non-volatile computer readable storage media.

User interface 110, application(s) 112, and context switch manager 114are stored in persistent storage 508 for execution by one or more of therespective computer processor(s) 504 via one or more memories of memory506. In this embodiment, persistent storage 508 includes a magnetic harddisk drive. Alternatively, or in addition to a magnetic hard disk drive,persistent storage 508 can include a solid-state hard drive, asemiconductor storage device, a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM), a flash memory, or any othercomputer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 508 may also be removable. Forexample, a removable hard drive may be used for persistent storage 508.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage508.

Communications unit 510, in these examples, provides for communicationswith other data processing systems or devices, including resources ofserver computer 104. In these examples, communications unit 510 includesone or more network interface cards. Communications unit 510 may providecommunications through the use of either or both physical and wirelesscommunications links. User interface 110, application(s) 112, andcontext switch manager 114 may be downloaded to persistent storage 508through communications unit 510.

I/O interface(s) 512 allows for input and output of data with otherdevices that may be connected to client computing device 108. Forexample, I/O interface(s) 512 may provide a connection to externaldevice(s) 518 such as a keyboard, a keypad, a touch screen, and/or someother suitable input device. External device(s) 518 can also includeportable computer readable storage media such as, for example, thumbdrives, portable optical or magnetic disks, and memory cards. Softwareand data used to practice embodiments of the present invention, e.g.,user interface 110, application(s) 112, and context switch manager 114,can be stored on such portable computer readable storage media and canbe loaded onto persistent storage 508 via I/O interface(s) 512. I/Ointerface(s) 512 also connect to a display 520.

Display 520 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be any tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network, and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers, and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including anobject-oriented programming language such as Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computer,or entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, a special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus, or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A method for grouping tasks initialized by a first user, the method comprising: receiving, by one or more computer processors, a first task initialization by a first user wherein a task is at least one of: an application, a tab within a window, or a process that has a user interface, and wherein a task represents a work unit that belongs to a work assignment of the first user; determining, by the one or more computer processors, whether one or more additional tasks contained in one or more task groups are in use by the first user; responsive to determining one or more additional tasks contained in one or more task groups are in use, determining, by the one or more computer processors, whether the first task is related to at least one task of the one or more additional tasks, wherein the first task and the at least one task are related by sharing one or more resources; and responsive to determining the first task is related to at least one task of the one or more additional tasks, adding, by the one or more computer processors, the first task to the task group containing the at least one related task of the one or more additional tasks.
 2. The method of claim 1, wherein the first task is in focus at first task initialization and wherein only one task is in focus at a particular point in time.
 3. The method of claim 1, further comprising: responsive to determining the first task is not related to at least one task of the one or more additional tasks, determining, by the one or more computer processors, whether an event is detected; responsive to determining an event is detected, generating, by the one or more computer processors, a new task group; and adding, by the one or more computer processors, the first task to the new task group.
 4. The method of claim 3, further comprising, responsive to determining an event is not detected, adding, by the one or more computer processors, the first task to a task group that contains a second task, wherein the second task is in focus immediately prior to the first task initialization.
 5. The method of claim 3, wherein an event includes an action initiated by a computing system of the first user, an action initiated by a second user, an action defined by the first user as an event, a break in activity of the first user, and closing a task group by the first user.
 6. The method of claim 1, further comprising: responsive to determining one or more additional tasks contained in one or more task groups are not in use, generating, by the one or more computer processors, a new task group; and adding, by the one or more computer processors, the first task to the new task group.
 7. The method of claim 1, further comprising: responsive to determining the first task is related to at least one of the one or more additional tasks, determining, by the one or more computer processors, whether the first task is related to at least one task in a first task group and at least one task in a second task group; and responsive to determining the first task is related to at least one task in a first task group and at least one task in a second task group, merging, by the one or more computer processors, the first and the second task groups into a merged task group, wherein the merged task group includes at least the first task and the first and the second task groups.
 8. The method of claim 1, wherein the first task is related to one or more additional tasks by a common work assignment of the first user that includes one or more of: a shared subject matter and a shared one or more resources, wherein a resource includes at least one of a directory, a file, a folder, a network port, a semaphore, a socket, a pipe, and a tag.
 9. The method of claim 1, further comprising: determining, by the one or more computer processors, at least one of the one or more tasks of the one or more task groups are inactive for a pre-defined threshold of time; and alerting, by the one or more computer processors, the first user of the inactivity. 